Sourced from serde_derive's releases.

v1.0.101

• Report errors on malformed serde attributes, like #[serde(rename =)] -- the compiler used to reject these itself, but when the compiler relaxed its requirements on attribute syntax these malformed attributes began silently being ignored by serde_derive

• Eliminate unused variable warning when using skip_serializing inside a tuple variant of an adjacently tagged enum (#1617, thanks @​arilotter)

• Support skip attribute inside of newtype variants (#1622, thanks @​Xaeroxe)

v1.0.100

• Provide serde::ser::StdError and serde::de::StdError which are either a re-export of std::error::Error (if Serde's "std" feature is enabled) or a new identical trait (otherwise).

  #[cfg(feature = "std")]
  pub use std::error::Error as StdError;
  
  #[cfg(not(feature = "std"))]
  pub trait StdError: Debug + Display {
      fn source(&self) -> Option<&(StdError + 'static)> { None }
  }

  Serde's error traits serde::ser::Error and serde::de::Error require std::error::Error as a supertrait, but only when Serde is built with "std" enabled. Data formats that don't care about no_std support should generally provide their error types with a std::error::Error impl directly:

  #[derive(Debug)]
  struct MySerError {...}
  
  impl serde::ser::Error for MySerError {...}
  
  impl std::fmt::Display for MySerError {...}
  
  // We don't support no_std!
  impl std::error::Error for MySerError {}

  Data formats that do support no_std may either have a "std" feature of their own as has been required in the past:

  [features]
  std = ["serde/std"]

  #[cfg(feature = "std")]
  impl std::error::Error for MySerError {}

  ... or else now may provide the std Error impl unconditionally via Serde's re-export:

  impl serde::ser::StdError for MySerError {}

... (truncated)

• 4aba6fa Release 1.0.101
• fe06bc2 More concise explanation of allow(unused_variables)
• 8dfb4cd Merge pull request #1617 from arilotter/master
• d1ade37 Ignore new too_many_lines lint
• 9de4924 Bug fix for #1610
• b24d501 Remove use of ref keyword from serde_derive
• e46463e Add tests for attribute parse errors
• a3157c9 Produce errors on attr that fails to parse as Meta
• 0d47226 Use flatten() to iterate serde meta items
• 7ab1259 Un-wrap error message strings for better grepping
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.